Establishing an IPSEC (internet protocol security) VPN (virtual private network) tunnel and encapsulating non-IP packets

ABSTRACT

Systems, methods and apparatuses of establishing an IPsec (Internet Protocol Security) VPN (Virtual Private Network) tunnel are disclosed. One method includes receiving, by a wireless mesh network access point, a user configuration, wherein the user configuration includes a type of traffic, determining an internal interface of the wireless mesh network access node based on the type of traffic, dynamically determining a local endpoint address for the IPsec VPN tunnel based on the selected internal interface, establishing the IPsec VPN tunnel through the selected internal interface of the wireless mesh network access node, and encapsulating non-IP packets of non-IP traffic within IP packets.

RELATED APPLICATION

This patent application in a continuation of U.S. patent applicationSer. No. 13/868,310, filed Apr. 23, 2103, which claims priority to U.S.Provisional Patent Application No. 61/694,846, filed on Aug. 30, 2012,which are all herein incorporated by reference.

FIELD OF THE DESCRIBED EMBODIMENTS

The described embodiments relate generally to wireless communications.More particularly, the described embodiments relate to systems, methodsand apparatuses for establishing an IPsec (Internet Protocol Security)VPN (Virtual Private Network) tunnel.

BACKGROUND

Internet Protocol Security (IPsec) is a protocol suite for securingInternet Protocol (IP) communications by authenticating and encryptingeach IP packet of a communication session. IPsec also includes protocolsfor establishing mutual authentication between agents at the beginningof the session and negotiation of cryptographic keys to be used duringthe session.

IPsec is an end-to-end security scheme operating in the Internet Layerof the Internet Protocol Suite. It can be used in protecting data flowsbetween a pair of hosts (host-to-host), between a pair of securitygateways (network-to-network), or between a security gateway and a host(network-to-host).

Typically, IPsec implementation inside a router requires a user to firstidentify the IP interface of the router. Further, the user is requiredto identify the router's IP address on which the traffic is originated.Further, the router is used as a local end-point in the IPsec tunnelsetup whenever possible. This is hard from the user's perspective sincethe user is required to have knowledge and understanding of the innerworking of the router and what the network interfaces are availableinside the router. This is even harder for the user if the traffic to beprotected must to go to a specific VLAN and/or the traffic involveserial data packets or other non-IP packets.

It is desirable to have methods and apparatuses for establishing anIPsec (Internet Protocol Security) VPN (Virtual Private Network) tunnelto a wireless access node of a wireless mesh network.

SUMMARY

An embodiment includes a method of establishing an IPsec (InternetProtocol Security) VPN (Virtual Private Network) tunnel. The methodincludes receiving, by an access node of a wireless mesh network, a userconfiguration, wherein the user configuration includes a type oftraffic, determining an internal interface of the access node based onthe type of traffic from at least one physical interface or at least onelogical interface, wherein if the type of traffic includes IP traffic,then one of the at least one physical interface is selected, and if thetype of traffic includes non-IP traffic, then one of the at least onelogical interface is selected, dynamically determining a local endpointaddress for the IPsec VPN tunnel based on whether the selected internalinterface is the one of the at least one physical interfaces, the one ofthe at least one logical interfaces, and whether another IPSec VPNtunnel is already utilizing the selected internal interface,establishing the IPsec VPN tunnel through the selected internalinterface of the wireless mesh network access node using the selectedlocal endpoint address, and encapsulating non-IP packets of non-IPtraffic within IP packets.

Another embodiment includes a wireless mesh network access node. Thewireless mesh network access node includes one or more transceivers forcommunicating with an upstream access node or a first upstream gatewayof a wireless mesh network, and a client device. The wireless meshnetwork access node further includes a controller. The controller isoperative to receive a user configuration, wherein the userconfiguration includes a type of traffic, select an internal interfaceof the access node based on the type of traffic from at least onephysical interface or at least one logical interface, wherein if thetype of traffic includes IP traffic, then one of the at least onephysical interface is selected, and if the type of traffic includesnon-IP traffic, then one of the at least one logical interface isselected, dynamically select a local endpoint address for the IPsec VPNtunnel based on whether the selected internal interface is the one ofthe at least one physical interfaces, the one of the at least onelogical interfaces, and whether another IPSec VPN tunnel is alreadyutilizing the selected internal interface, establish the IPsec VPNtunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address, andencapsulate non-IP packets of non-IP traffic within IP packets.

Another embodiment includes a system for establishing an IPsec (InternetProtocol Security) VPN (Virtual Private Network) tunnel. The systemincludes a gateway and a wireless mesh network access point wirelesslyconnected to the gateway. The wireless mesh network access point isoperative to receive a user configuration, wherein the userconfiguration includes a type of traffic, select an internal interfaceof the access node based on the type of traffic from at least onephysical interface or at least one logical interface, wherein if thetype of traffic includes IP traffic, then one of the at least onephysical interface is selected, and if the type of traffic includesnon-IP traffic, then one of the at least one logical interface isselected, dynamically select a local endpoint address for the IPsec VPNtunnel based on whether the selected internal interface is the one ofthe at least one physical interfaces, the one of the at least onelogical interfaces, and whether another IPSec VPN tunnel is alreadyutilizing the selected internal interface, establish the IPsec VPNtunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address, andencapsulate non-IP packets of non-IP traffic within IP packets.

Other aspects and advantages of the described embodiments will becomeapparent from the following detailed description, taken in conjunctionwith the accompanying drawings, illustrating by way of example theprinciples of the described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an IPsec VPN tunnel formed between an access node and aremote endpoint VPN device, according to an embodiment.

FIG. 2 shows an IPsec VPN tunnel formed between a wireless mesh networkaccess node of a wireless mesh network and a remote endpoint VPN device,according to an embodiment.

FIG. 3 shows a flow chart that includes steps of a method ofestablishing an IPsec (Internet Protocol Security) VPN (Virtual PrivateNetwork) tunnel.

FIG. 4 show an access node, according to an embodiment.

DETAILED DESCRIPTION

The embodiments described provide systems, methods and apparatuses forestablishing an IPsec (Internet Protocol Security) VPN (Virtual PrivateNetwork) tunnel between an access node of a wireless mesh network and aremote device. The described embodiments include identifying what typeof data traffic that needs to be protected. The type of data traffic canrange from wireless traffic, wired traffic, AMI/C12.22 traffic,Serial/DNP3 traffic, or all the above traffic combined along with theVLAN number associated with the data traffic. Once the data traffic typeis identified, the VPN server (remote end of the IPsec tunnel) alongwith the private networks that the IPsec tunnel will serve isconfigured.

When a user selects the traffic type (for example, through a userconfiguration), for at least some of the described embodiments,processing of the wireless access node determines what internalinterfaces of the wireless access node to use. For example, for wiredtraffic coming in to the wireless access node from an Ethernet interface(eth1) (which is IP traffic), the processing may designate an eth1 IPaddress (which is a physical interface) as the local endpoint of anIPsec VPN tunnel being established. For example, for AMI traffic orserial traffic (which is non-IP traffic), the processing may designate alogical interface (as opposed to a physical interface) as an internalinterface. For both selections of a physical interface or a logicalinterface, another interface may be selected for determining the localend point address for the IPsec VPN tunnel being established.

There are many types of VPNs (Virtual Private Networks) available foruse in today's networks. One of these types involves use of the IPSecstandard. Within IPSec, there are further options on ways to define theVPN. The actual building or construction of the IPSec VPN is veryinvolved. Like other VPNs, an IPSec tunnel is secure, and is encryptedusing cryptographic techniques.

FIG. 1 shows an IPsec VPN tunnel 150 formed between an access node 110and a remote endpoint VPN device 130, according to an embodiment. Asshown, the access node 110 includes multiple interfaces, includinglogical interfaces 112, 114, and physical or real interfaces 116, 118.It is to be understood that while only two logical interfaces 112, 114,and two physical 116, 118 are shown, any number of logical interfacesand physical interfaces are possible.

The access node 110 receives a user configuration, which can be selectedor determined by a system operator. Generally, the system operator auser that uses, owns or manages the wireless access node and/or thewireless mesh network. For at least some embodiments, the systemoperator selects which local and remote networks to be secured. Further,for an embodiment, the system operator specifies the remote tunnelendpoint device. Further, for an embodiment, the system operatorspecifies type of traffic. However, for at least some embodiments, thesystem operator does not select the local end point address of the IPsecVPN tunnel. As will be described, at least some of the describedembodiments include the local end point address of the IPsec VPN tunnelbeing determined at or by the access node of the wireless mesh network.

The user configuration includes a traffic type. Based on the traffictype, the access node 110 determines an internal interface to be aphysical interface or a logical interface. Further, the access node 110dynamically determines a local endpoint address for an IPsec VPN tunnel150 based on one of the logical interfaces 112, 114, or one of thephysical interfaces 116, 118. Finally, the access node 110 establishesthe IPsec VPN tunnel through the selected internal interface of theaccess node 110 based on the local endpoint address. In this example,the logical interface 114 is selected as the local endpoint address. Itis to be understood that the sequence of actions do not have to followthe order described.

As described, an embodiment includes determining the internal interfacewhere the source of traffic is originating whether the source of thetraffic includes IP traffic (wired or wireless, with or without VLAN),or non IP traffic. For the IP traffic, the internal interface can bemore likely to be the physical interface. For non-IP traffic, at leastsome embodiments include selecting or creating a new logical interfaceto bind the non-IP traffic to IP traffic.

Further, as described, at least some embodiments include dynamicallydetermining the local endpoint interface. For at least some embodiments,this includes determining whether local endpoint interface correspondswith the internal interface identified previously determined, or whetheranother logical interface needs to be created. For at least someembodiments, this is dependent on whether the selected interface isavailable (for example, another IPsec VPN may already be utilizing theinternal interface) and stable (that is, consistently connected). If anew local-end point interface must be created, at least some embodimentsinclude obtaining an IP address from the wireless mesh network (thisincludes, for example, performing a DHCP (Dynamic Host ConfigurationProtocol) over the mesh network), and then advertising the IP addressand the corresponding routes throughout the wireless mesh network.

As stated, an embodiment includes determining the internal interface ofthe access node based on the type of traffic. For an embodiment, theinternal interface is selected from at least one physical interface orat least one logical interface, wherein if the type of traffic includesIP traffic, then one of the at least one physical interface is selected,and if the type of traffic includes non-IP traffic, then one of the atleast one logical interface is selected. A logical interface 111 isdepicted in FIG. 1 to illustrate that selection (creation) of thelogical interface 111 if the data traffic is non-IP traffic.

For at least some embodiments, the logical interface 111 is used by aprogram that processes non-IP traffic to IP traffic and vice versa. Thisprogram, such as a DNP3 (Distributed Network Protocol) program takes IPtraffic, extracts serial data, and then sends it to a DNP3 device. Forexample, the client device 142 may be a DNP3 device. Thus, the remotedevice (for example, Serial DNP3 master) that wants to access the serialdevice (for example, Serial DNP3 client) connected to the access node110 uses the IP address of the logical-interface-111. However, thetraffic goes through the IPsec VPN tunnel by the access node 110. Ifprior to using IPsec tunnel, the non-IP traffic was bound to a differentlogical interface or even a physical interface, then the latterinterface IP address must be de-advertise throughout the wireless meshnetwork.

For an embodiment, dynamically determining the local endpoint addressfor the IPsec VPN tunnel is based on whether the selected internalinterface is the one of the at least one physical interfaces, the one ofthe at least one logical interfaces, and whether another IPSec VPNtunnel is already utilizing the selected internal interface.

As previously stated, an embodiment includes establishing the IPsec VPNtunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address.

For an embodiment, the access node includes an internal map that mapsthe selected internal interface with the type of traffic. That is, whenthe access node receives the user configuration, the type of trafficwithin the user configuration is used to select the internal interfaceby accessing the internal map. For an embodiment, the map includes alook-up-table that provides a selected interface based on the type oftraffic. As described, the internal interface can includes a physicalinterface or a logical interface, which for an embodiment, are selectedbased on whether the type of traffic includes IP packets or non-IPpackets.

For an embodiment, the at least one logical interface is not tied to aphysical port, and created to send and receive IP traffic. For anembodiment, the selected logical interface facilitates encapsulatingnon-IP packets of non-IP traffic within IP packets. For an embodiment,determining at least one logical interface for non-IP traffic includescreating the at least one logical interface with an IP address forencapsulating non-IP packets into IP packets, communicating the IPaddress to a remote VPN device, and de-advertising a route for the IPaddress in the wireless mesh network if the IP address is beingadvertised so that the at least one logical interface cannot be accesseddirectly without going through the IPsec VPN tunnel. If the user orsystem operator selects non-IP traffic, a logical interface is createdwith an IP address to encapsulate the IP packets. Even though this IPaddress needs to be communicated to the remote VPN device (so that theremote VPN device can build IPsec rules), the route for this IP addressin the mesh network needs to be de-advertised so that any remote devicescannot access this IP address directly. Rather, the remote device needsto access the logical interface through the IPsec tunnel for the non-IPtraffic.

For at least some embodiments, the selection of the local endpointaddress is dependent on whether a physical interface or a logicalinterface was selected. Further, the selection of the local endpointaddress is dependent on whether a prior IPsec VPN tunnel is using theselected physical interface. Further, the selection of the localendpoint address is dependent whether the selected internal interfaceincludes the one of the at least one physical interface on a same VLAN(Virtual Local Area Network) as specified by the user configuration.

Physical Interface

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of the selected physical interface if the selectedinternal interface includes the one of the at least one physicalinterface physical interface, and a prior IPsec VPN tunnel is not usingthe selected physical interface.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface, anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one physical interface, and a prior IPsec VPN tunnel isusing the selected physical interface.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of the selected physical interface if the selectedinternal interface includes the one of the at least one physicalinterface on a same VLAN (Virtual Local Area Network) as specified bythe user configuration.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one physical interface and an available physical interfaceis not on a same VLAN (Virtual Local Area Network) as specified by theuser configuration.

Logical Interface

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of an available physical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of an available physical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic, and the selectedphysical interface is on a same VLAN (Virtual Local Area Network) asspecified by the user configuration.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one logical interface that was selected for non-IP trafficand no physical interface is available.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one logical interface that was selected for non-IP trafficand an available physical interface is not on a same VLAN (Virtual LocalArea Network) as specified by the user configuration.

An embodiment further includes communicating the selected internalinterface to a remote device if the selected internal interface includesa logical interface, and statically configuring an IP (internetprotocol) using the logical interface. For an embodiment, the IP addresscan be obtained statically using the user configuration or DHCP.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes advertising to the wireless mesh network,the selected local endpoint address if the selected local endpointaddress was selected based on creation of a new logical interface,thereby allowing establishment of the IPsec VPN tunnel.

FIG. 2 shows an IPsec VPN tunnel formed between a wireless mesh networkaccess node 231 of a wireless mesh network and a remote endpoint VPNdevice 130, according to an embodiment. Here, the access node 231 has anupstream wireless link to an upstream access node 230, which has anupstream wireless link to a gateway 220. It is to be understood that thedescribe embodiments for establishing an IPsec (Internet ProtocolSecurity) VPN (Virtual Private Network) tunnel are applicable to any ofthe access nodes of the wireless mesh network. The IPsec (InternetProtocol Security) VPN (Virtual Private Network) tunnel is formedbetween the access node 231 and the remote endpoint VPN device 130. Foran embodiment, the IPsec (Internet Protocol Security) VPN (VirtualPrivate Network) tunnel is formed through the internet 120 and at leasta portion of the wireless mesh network.

While only one upstream access node 230 is shown, it is to be understoodthat any number of upstream access nodes can be included between theaccess node 231 and the gateway 220. For at least some embodiments, theupstream access nodes and the gateway 220 maintain routing tables 243,245 that allow the upstream access nodes and the gateway 220 to properlyroute packets received to the access node 231. The upstream access nodesand gateway 220 also maintain the routing tables associated with theclient 240,241 and/or 242 if received IP packets are not going throughthe IPsec tunnel, otherwise the routing tables associated with theselected endpoint addresses inside node 231 are maintained within therouting tables. Additionally, the access node 231 maintains a routingtable to allow the access node 231 to properly route received packets toother downstream devices if any. Further, the routing tables allow theaccess nodes to properly route upstream data packets as well. That is,each access nodes must also maintain the routing table of theirimmediate upstream node (also referred to as a ‘default route’). Forexample, for AN230, maintains the default route to GW220.

An embodiment includes the access node 231 advertising an IP address ofa new logical interface to any upstream access nodes and the upstreamgateway of the wireless mesh network if the local endpoint address wasdetermined based on the new logical interface, thereby allowing the anyupstream access nodes and the upstream gateway to establish a route tothe access node based on the IP address.

If, for example, if the gateway 220 receives one or more IP packets witha destination address having the endpoint IP address, the gateway 220knows how to route the packet through the wireless mesh network based ona routing table of the gateway 220 that has been updated, for example,with local endpoint address. The gateway 220 then routes the IP packetto the access node or an access node that is downstream to the gateway220 but upstream to the access node 231. Again, this is facilitated byupdated routing tables of the gateway and updated routing tables of theupstream access nodes.

For an embodiment, the gateway 220 advertises the endpoint address toother gateways of the wireless mesh network in case the access node 231later selects a route through a different upstream gateway of thewireless mesh network.

For an embodiment, the gateway 220 communicates endpoint address toupstream network (outside the mesh) so that upstream network know how toroute packets having a destination address of the endpoint address.

FIG. 3 shows a flow chart that includes steps of a method ofestablishing an IPsec (Internet Protocol Security) VPN (Virtual PrivateNetwork) tunnel. A first step 310 includes receiving, by a wireless meshnetwork access point, a user configuration, wherein the userconfiguration includes a type of traffic. A second step 320 includesdetermining an internal interface of the access node based on the typeof traffic from at least one physical interface or at least one logicalinterface, wherein if the type of traffic includes IP traffic, then oneof the at least one physical interface is selected, and if the type oftraffic includes non-IP traffic, then one of the at least one logicalinterface is selected. A third step 330 includes dynamically determininga local endpoint address for the IPsec VPN tunnel based on whether theselected internal interface is the one of the at least one physicalinterfaces, the one of the at least one logical interfaces, and whetheranother IPSec VPN tunnel is already utilizing the selected internalinterface. A fourth step 340 includes establishing the IPsec VPN tunnelthrough the selected internal interface of the wireless mesh networkaccess node using the selected local endpoint address.

For an embodiment, the access node further comprises an internal mapthat maps the selected internal interface with the type of traffic.

For an embodiment, the at least one logical interface is not tied to aphysical port, and created to send and receive IP traffic. An embodimentfurther includes encapsulating non-IP packets of non-IP traffic withinIP packets. For an embodiment, determining at least one logicalinterface for non-IP traffic includes creating the at least one logicalinterface with an IP address for encapsulating non-IP packets into IPpackets and communicating the IP address to a remote VPN device. Anembodiment further includes de-advertising a route for the IP address inthe wireless mesh network if the IP address was previously advertised,thereby preventing the IP address from being accessed directly withoutgoing through the IPsec VPN tunnel.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of the selected physical interface if the selectedinternal interface includes the one of the at least one physicalinterface physical interface, and a prior IPsec VPN tunnel is not usingthe selected physical interface.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface, anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one physical interface, and a prior IPsec VPN tunnel isusing the selected physical interface.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of the selected physical interface if the selectedinternal interface includes the one of the at least one physicalinterface on a same VLAN (Virtual Local Area Network) as specified bythe user configuration.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one physical interface and an available physical interfaceis not on a same VLAN (Virtual Local Area Network) as specified by theuser configuration.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of an available physical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes determining the local endpoint address tobe an address of an available physical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic, and the selectedphysical interface is on a same VLAN (Virtual Local Area Network) asspecified by the user configuration.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one logical interface that was selected for non-IP trafficand no physical interface is available.

For an embodiment, dynamically determining a local endpoint address forthe IPsec VPN tunnel includes creating a new logical interface anddetermining the local endpoint address to be an address of the newlogical interface if the selected internal interface includes the one ofthe at least one logical interface that was selected for non-IP trafficand an available physical interface is not on a same VLAN (Virtual LocalArea Network) as specified by the user configuration.

An embodiment further includes communicating the selected internalinterface to a remote device if the selected internal interface includesa logical interface, and statically configuring an IP (internetprotocol) using the logical interface.

An embodiment further includes advertising to the wireless mesh network,the selected local endpoint address if the selected local endpointaddress was selected based on creation of a new logical interface,thereby allowing establishment of the IPsec VPN tunnel.

FIG. 4 show a wireless mesh network access node 400, according to anembodiment. The wireless mesh network access node 400 includes one ormore transceivers 420 for communicating with an upstream access node ora first upstream gateway of a wireless mesh network, and a clientdevice. The transceivers can be wired or wireless. The wireless meshnetwork access node 400 further includes a controller 400. For anembodiment, the controller is operative to receive a user configuration,wherein the user configuration includes a type of traffic, select aninternal interface of the access node based on the type of traffic fromat least one physical interface or at least one logical interface,wherein if the type of traffic includes IP traffic, then one of the atleast one physical interface is selected, and if the type of trafficincludes non-IP traffic, then one of the at least one logical interfaceis selected, dynamically select a local endpoint address for the IPsecVPN tunnel based on whether the selected internal interface is the oneof the at least one physical interfaces, the one of the at least onelogical interfaces, and whether another IPSec VPN tunnel is alreadyutilizing the selected internal interface, and establish the IPsec VPNtunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address.

As previously described, for an embodiment, the access node furthercomprises an internal map that maps the selected internal interface withthe type of traffic.

As previously described, for an embodiment, the at least one logicalinterface is not tied to a physical port, and created to send andreceive IP traffic. An embodiment further includes encapsulating non-IPpackets of non-IP traffic within IP packets. For an embodiment,determining at least one logical interface for non-IP traffic includescreating the at least one logical interface with an IP address forencapsulating non-IP packets into IP packets and communicating the IPaddress to a remote VPN device. An embodiment further includesde-advertising a route for the IP address in the wireless mesh networkif the IP address was previously advertised, thereby preventing the IPaddress from being accessed directly without going through the IPsec VPNtunnel.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includesdetermining the local endpoint address to be an address of the selectedphysical interface if the selected internal interface includes the oneof the at least one physical interface physical interface, and a priorIPsec VPN tunnel is not using the selected physical interface.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includescreating a new logical interface, and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one physicalinterface, and a prior IPsec VPN tunnel is using the selected physicalinterface.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includesdetermining the local endpoint address to be an address of the selectedphysical interface if the selected internal interface includes the oneof the at least one physical interface on a same VLAN (Virtual LocalArea Network) as specified by the user configuration.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includescreating a new logical interface and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one physicalinterface and an available physical interface is not on a same VLAN(Virtual Local Area Network) as specified by the user configuration.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includesdetermining the local endpoint address to be an address of an availablephysical interface if the selected internal interface includes the oneof the at least one logical interface that was selected for non-IPtraffic.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includesdetermining the local endpoint address to be an address of an availablephysical interface if the selected internal interface includes the oneof the at least one logical interface that was selected for non-IPtraffic, and the selected physical interface is on a same VLAN (VirtualLocal Area Network) as specified by the user configuration.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includescreating a new logical interface and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic and no physical interfaceis available.

As previously described, for an embodiment, the access node dynamicallydetermining a local endpoint address for the IPsec VPN tunnel includescreating a new logical interface and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic and an available physicalinterface is not on a same VLAN (Virtual Local Area Network) asspecified by the user configuration.

As previously described, an embodiment further includes the access nodecommunicating the selected internal interface to a remote device if theselected internal interface includes a logical interface, and staticallyconfiguring an IP (internet protocol) using the logical interface.

As previously described, an embodiment further includes the access nodeadvertising to the wireless mesh network, the selected local endpointaddress if the selected local endpoint address was selected based oncreation of a new logical interface, thereby allowing establishment ofthe IPsec VPN tunnel.

ADDITIONAL EMBODIMENTS

As described, at least some embodiments include establishment of theIPsec VPN tunnel. An embodiment includes IPsec Auto Tunnel EstablishmentUsing Ping Packets. Existing methods for setting up an IP VPN tunnelbetween a client device and a remote network require activity by theclient device in order for the tunnel to be established. If there is noactivity by the client, no tunnel is established. However, at least someof the embodiments described here do not require the client device to beactive. The described embodiments include the establishment of an IP VPNtunnel based on a router receiving a client configuration.

An embodiment includes a method of establishing an IPsec (InternetProtocol Security) VPN (Virtual Private Network) tunnel. The methodincludes receiving, by a router (such as the previously describewireless access node), a client configuration (the client can be activeor not. The method further includes selecting, by the router, an IPaddress, wherein the selected IP address is within a range provided bythe client configuration, assigning, by the router, the selected IPaddress to a temporary logical interface. The method further includes,sending, by the router, a ping packet from the temporary logicalinterface to a remote network (as defined by the client configuration)to open an IPsec VPN tunnel between the router and the remote network,and removing, by the router, the temporary logical interface once theIPsec VPN tunnel is open. At least some embodiments further includere-sending, by the router, another ping packet from the temporarylogical interface to the remote network if an error is received from theremote network.

An embodiment includes a router (such as the previously describedwireless access node) wherein the router includes one or more processorsoperative to receive a client configuration; (the client can be activeor not), select an IP address, wherein the selected IP address is withina range provided by the client configuration, assign the selected IPaddress to a virtual interface, send a ping packet from the virtualinterface to a remote network (as defined by the client configuration)to open an IPsec (Internet Protocol Security) VPN (Virtual PrivateNetwork) tunnel between the router and the remote network, and removethe virtual interface once the IPsec VPN tunnel is open. An embodimentof the router further includes the one or more processors operative tore-send another ping packet from the virtual interface to the remotenetwork if an error is received from the remote network.

Although specific embodiments have been described and illustrated, theembodiments are not to be limited to the specific forms or arrangementsof parts so described and illustrated.

What is claimed:
 1. A method of establishing an IPsec (Internet ProtocolSecurity) VPN (Virtual Private Network) tunnel, comprising: receiving,by an access node of a wireless mesh network, a user configuration,wherein the user configuration includes a type of traffic; determiningan internal interface of the access node based on the type of trafficfrom at least one physical interface or at least one logical interface,wherein if the type of traffic includes IP traffic, then one of the atleast one physical interface is selected, and if the type of trafficincludes non-IP traffic, then one of the at least one logical interfaceis selected; dynamically determining a local endpoint address for theIPsec VPN tunnel based on whether the selected internal interface is theone of the at least one physical interfaces, the one of the at least onelogical interfaces, and whether another IPSec VPN tunnel is alreadyutilizing the selected internal interface, wherein dynamicallydetermining the local endpoint address for the IPsec VPN tunnelcomprises determining the local endpoint address to be an address of theselected physical interface if the selected internal interface includesthe one of the at least one physical interface physical interface, and aprior IPsec VPN tunnel is not using the selected physical interface;establishing the IPsec VPN tunnel through the selected internalinterface of the wireless mesh network access node using the selectedlocal endpoint address; and encapsulating non-IP packets of non-IPtraffic within IP packets.
 2. The method of claim 1, wherein the accessnode further comprises an internal map that maps the selected internalinterface with the type of traffic.
 3. The method of claim 1, whereinthe at least one logical interface is not tied to a physical port, andcreated to send and receive IP traffic.
 4. The method of claim 1,further comprising advertising an IP address of a new logical interfaceto any upstream access nodes and the upstream gateway of the wirelessmesh network if the local endpoint address was determined based on thenew logical interface, thereby allowing the any upstream access nodesand the upstream gateway to establish a route to the access node basedon the IP address.
 5. The method of claim 1, wherein determining atleast one logical interface for non-IP traffic includes: creating the atleast one logical interface with an IP address for encapsulating non-IPpackets into IP packets; and communicating the IP address to a remoteVPN device.
 6. The method of claim 5, further comprising de-advertisinga route for the IP address in the wireless mesh network if the IPaddress was previously advertised, thereby preventing the IP addressfrom being accessed directly without going through the IPsec VPN tunnel.7. The method of claim 1, wherein dynamically determining a localendpoint address for the IPsec VPN tunnel comprises: creating a newlogical interface, and determining the local endpoint address to be anaddress of the new logical interface if the selected internal interfaceincludes the one of the at least one physical interface, and a priorIPsec VPN tunnel is using the selected physical interface.
 8. The methodof claim 1, wherein dynamically determining a local endpoint address forthe IPsec VPN tunnel comprises: determining the local endpoint addressto be an address of the selected physical interface if the selectedinternal interface includes the one of the at least one physicalinterface on a same VLAN (Virtual Local Area Network) as specified bythe user configuration.
 9. The method of claim 1, wherein dynamicallydetermining a local endpoint address for the IPsec VPN tunnel comprises:creating a new logical interface and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one physicalinterface and an available physical interface is not on a same VLAN(Virtual Local Area Network) as specified by the user configuration. 10.The method of claim 1, wherein dynamically determining a local endpointaddress for the IPsec VPN tunnel comprises: determining the localendpoint address to be an address of an available physical interface ifthe selected internal interface includes the one of the at least onelogical interface that was selected for non-IP traffic.
 11. The methodof claim 1, wherein dynamically determining a local endpoint address forthe IPsec VPN tunnel comprises: determining the local endpoint addressto be an address of an available physical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic, and the selectedphysical interface is on a same VLAN (Virtual Local Area Network) asspecified by the user configuration.
 12. The method of claim 1, whereindynamically determining a local endpoint address for the IPsec VPNtunnel comprises: creating a new logical interface and determining thelocal endpoint address to be an address of the new logical interface ifthe selected internal interface includes the one of the at least onelogical interface that was selected for non-IP traffic and no physicalinterface is available.
 13. The method of claim 1, wherein dynamicallydetermining a local endpoint address for the IPsec VPN tunnel comprises:creating a new logical interface and determining the local endpointaddress to be an address of the new logical interface if the selectedinternal interface includes the one of the at least one logicalinterface that was selected for non-IP traffic and an available physicalinterface is not on a same VLAN (Virtual Local Area Network) asspecified by the user configuration.
 14. The method of claim 1, furthercomprising communicating the selected internal interface to a remotedevice if the selected internal interface includes a logical interface,and statically configuring an IP (internet protocol) using the logicalinterface.
 15. The method of claim 1, further comprising advertising tothe wireless mesh network, the selected local endpoint address if theselected local endpoint address was selected based on creation of a newlogical interface, thereby allowing establishment of the IPsec VPNtunnel.
 16. A wireless mesh network access node, comprising: one or moretransceivers for communicating with an upstream access node or anupstream gateway of a wireless mesh network, and a client device; acontroller, the controller operative to: receive a user configuration,wherein the user configuration includes a type of traffic; select aninternal interface of the access node based on the type of traffic fromat least one physical interface or at least one logical interface,wherein if the type of traffic includes IP traffic, then one of the atleast one physical interface is selected, and if the type of trafficincludes non-IP traffic, then one of the at least one logical interfaceis selected; dynamically select a local endpoint address for the IPsecVPN tunnel based on whether the selected internal interface is the oneof the at least one physical interfaces, the one of the at least onelogical interfaces, and whether another IPSec VPN tunnel is alreadyutilizing the selected internal interface, wherein dynamically selectingthe local endpoint address for the IPsec VPN tunnel comprises selectingthe local endpoint address to be an address of the selected physicalinterface if the selected internal interface includes the one of the atleast one physical interface physical interface, and a prior IPsec VPNtunnel is not using the selected physical interface; establish the IPsecVPN tunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address; andencapsulate non-IP packets of non-IP traffic within IP packets.
 17. Thewireless mesh network access node of claim 16, wherein determining atleast one logical interface for non-IP traffic includes the controlleroperative to: create the at least one logical interface with an IPaddress for encapsulating non-IP packets into IP packets; communicatethe IP address to a remote VPN device.
 18. The wireless mesh networkaccess node of claim 17, wherein the controller is further operative to:de-advertise a route for the IP address in the wireless mesh network ifthe IP address was previously advertised, thereby preventing the IPaddress from being accessed directly without going through the IPsec VPNtunnel.
 19. A system for establishing an IPsec (Internet ProtocolSecurity) VPN (Virtual Private Network) tunnel, comprising: a gateway; awireless mesh network access point wirelessly connected to the gateway,wherein the wireless mesh network access point is operative to: receivea user configuration, wherein the user configuration includes a type oftraffic; determine an internal interface of the wireless mesh networkaccess node based on the type of traffic from at least one physicalinterface or at least one logical interface, wherein if the type oftraffic includes IP traffic, then one of the at least one physicalinterface is selected, and if the type of traffic includes non-IPtraffic, then one of the at least one logical interface is selected;dynamically determine a local endpoint address for the IPsec VPN tunnelbased on whether the selected internal interface is the one of the atleast one physical interfaces, the one of the at least one logicalinterfaces, and whether another IPSec VPN tunnel is already utilizingthe selected internal interface, wherein dynamically determining thelocal endpoint address for the IPsec VPN tunnel comprises determiningthe local endpoint address to be an address of the selected physicalinterface if the selected internal interface includes the one of the atleast one physical interface physical interface, and a prior IPsec VPNtunnel is not using the selected physical interface; establish the IPsecVPN tunnel through the selected internal interface of the wireless meshnetwork access node using the selected local endpoint address; andencapsulating non-IP packets of non-IP traffic within IP packets.